Screen Timeout Duration

ABSTRACT

In one embodiment, a method includes determining for each of multiple countdowns to an automatic screen timeout of a computing device whether the countdown was too long or too short. The countdown is too short if user interaction with the computing device occurred within a first pre-determined amount of time after the automatic screen timeout. The countdown is too long if user interaction with the computing device turned off a screen of the computing device prior to a second pre-determined amount of time before the automatic screen timeout. The method includes determining an underage of each of one or more of the countdowns that was too short; determining an overage of each of one or more of the countdowns that was too long; and adjusting a countdown length of the automatic screen timeout based at least in part on the underages or overages.

PRIORITY

This application is a continuation under 35 U.S.C. § 120 of U.S. patentapplication Ser. No. 13/663,132, filed 29 Oct. 2012, which isincorporated herein by reference.

TECHNICAL FIELD

This disclosure generally relates to screen-timeout functionality of acomputing device.

BACKGROUND

A mobile computing device—such as a smartphone, tablet computer, orlaptop computer—may include functionality for determining its location,direction, or orientation, such as a GPS receiver, compass, orgyroscope. Such a device may also include functionality for wirelesscommunication, such as BLUETOOTH communication, near-field communication(NFC), or infrared (IR) communication or communication with a wirelesslocal area networks (WLANs) or cellular-telephone network. Such a devicemay also include one or more cameras, scanners, touchscreens,microphones, or speakers. Mobile computing devices may also executesoftware applications, such as games, web browsers, or social-networkingapplications. With social-networking applications, users may connect,communicate, and share information with other users in their socialnetworks.

SUMMARY OF PARTICULAR EMBODIMENTS

Users of a mobile computing device may have experiences where theduration of an automatic screen timeout is too short or too long.Particular embodiments illustrate examples of adjusting the automaticscreen timeout to be longer or shorter based on whether the automaticscreen timeout was too short or too long.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example network environment associated with asocial-networking system.

FIG. 2 illustrates example timeline of an example automatic screentimeout.

FIG. 3 illustrates an example method for adjusting a length of acountdown.

FIG. 4 illustrates another example method for adjusting a length of acountdown.

FIG. 5 illustrates an example computer system.

DESCRIPTION OF EXAMPLE EMBODIMENTS

FIG. 1 illustrates an example network environment 100 associated with asocial-networking system. Network environment 100 includes a user 101, aclient system 130, and a social-networking system 160, connected to eachother by a network 110. Although FIG. 1 illustrates a particulararrangement of user 101, client system 130, social-networking system160, and network 110, this disclosure contemplates any suitablearrangement of user 101, client system 130, social-networking system160, and network 110. As an example and not by way of limitation, two ormore of client system 130, and social-networking system 160, may beconnected to each other directly, bypassing network 110. As anotherexample, two or more of client system 130, and social-networking system160 may be physically or logically co-located with each other in wholeor in part. Moreover, although FIG. 1 illustrates a particular number ofusers 101, client systems 130, social-networking systems 160, andnetworks 110, this disclosure contemplates any suitable number of users101, client systems 130, social-networking systems 160, and networks110. As an example and not by way of limitation, network environment 100may include multiple users 101, client system 130, social-networkingsystems 160, and networks 110.

In particular embodiments, user 101 may be an individual (human user),an entity (e.g., an enterprise, business, or third-party application),or a group (e.g., of individuals or entities) that interacts orcommunicates with or over social-networking system 160. In particularembodiments, one or more users 101 may use one or more client systems130 to access, send data to, and receive data from social-networkingsystem 160.

In particular embodiments, social-networking system 160 may be anetwork-addressable computing system that can host an online socialnetwork. Social-networking system 160 may generate, store, receive, andtransmit social-networking data, such as, for example, user-profiledata, concept-profile data, social-graph information, or other suitabledata related to the online social network. Social-networking system 160may be accessed by the other components of network environment 100either directly or via network 110. In particular embodiments,social-networking system 160 may include one or more servers 162. Eachserver 162 may be a unitary server or a distributed server spanningmultiple computers or multiple datacenters. Servers 162 may be ofvarious types, such as, for example and without limitation, web server,news server, mail server, message server, advertising server, fileserver, application server, exchange server, database server, proxyserver, another server suitable for performing functions or processesdescribed herein, or any combination thereof. In particular embodiments,each server 162 may include hardware, software, or embedded logiccomponents or a combination of two or more such components for carryingout the appropriate functionalities implemented or supported by server162. In particular embodiments, social-networking system 164 may includeone or more data stores 164. Data stores 164 may be used to storevarious types of information. In particular embodiments, the informationstored in data stores 164 may be organized according to specific datastructures. In particular embodiments, each data store 164 may be arelational database. Particular embodiments may provide interfaces thatenable a client system 130, a social-networking system 160, or athird-party system to manage, retrieve, modify, add, or delete, theinformation stored in data store 164.

In particular embodiments, social-networking system 160 may store one ormore social graphs in one or more data stores 164. In particularembodiments, a social graph may include multiple nodes—which may includemultiple user nodes (each corresponding to a particular user) ormultiple concept nodes (each corresponding to a particular concept)—andmultiple edges connecting the nodes. Social-networking system 160 mayprovide users of the online social network the ability to communicateand interact with other users. In particular embodiments, users may jointhe online social network via social-networking system 160 and then addconnections (i.e., relationships) to a number of other users ofsocial-networking system 160 whom they want to be connected to. Herein,the term “friend” may refer to any other user of social-networkingsystem 160 with whom a user has formed a connection, association, orrelationship via social-networking system 160.

In particular embodiments, social-networking system 160 may provideusers with the ability to take actions on various types of items orobjects, supported by social-networking system 160. As an example andnot by way of limitation, the items and objects may include groups orsocial networks to which users of social-networking system 160 maybelong, events or calendar entries in which a user might be interested,computer-based applications that a user may use, transactions that allowusers to buy or sell items via the service, interactions withadvertisements that a user may perform, or other suitable items orobjects. A user may interact with anything that is capable of beingrepresented in social-networking system 160 or by an external system ofa third-party system, which is separate from social-networking system160 and coupled to social-networking system 160 via a network 110. Inparticular embodiments, social-networking system 160 may include anauthorization server that allows users 101 to opt in or opt out ofhaving their actions logged by social-networking system 160 or sharedwith other systems (e.g., third-party systems), such as, for example, bysetting appropriate privacy settings.

In particular embodiments, social-networking system 160 may include avariety of servers, sub-systems, programs, modules, logs, and datastores. In particular embodiments, social-networking system 160 mayinclude one or more of the following: a web server, action logger,API-request server, relevance-and-ranking engine, content-objectclassifier, notification controller, action log,third-party-content-object-exposure log, inference module,authorization/privacy server, search module, ad-targeting module,user-interface module, user-profile store, connection store, third-partycontent store, or location store. Social-networking system 160 may alsoinclude suitable components such as network interfaces, securitymechanisms, load balancers, failover servers,management-and-network-operations consoles, other suitable components,or any suitable combination thereof. In particular embodiments,social-networking system 160 may include one or more user-profile storesfor storing user profiles. A user profile may include, for example,biographic information, demographic information, behavioral information,social information, or other types of descriptive information, such aswork experience, educational history, hobbies or preferences, interests,affinities, or location. Interest information may include interestsrelated to one or more categories. Categories may be general orspecific. As an example and not by way of limitation, if a user “likes”an article about a brand of shoes the category may be the brand, or thegeneral category of “shoes” or “clothing.”

This disclosure contemplates any suitable network 110. As an example andnot by way of limitation, one or more portions of network 110 mayinclude an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), a portion of the Internet, a portion of the Public SwitchedTelephone Network (PSTN), a cellular telephone network, or a combinationof two or more of these. Network 110 may include one or more networks110.

Links 150 may connect client system 130 and social-networking system 160to communication network 110 or to each other. This disclosurecontemplates any suitable links 150. In particular embodiments, one ormore links 150 include one or more wireline (such as for example DigitalSubscriber Line (DSL) or Data Over Cable Service Interface Specification(DOCSIS)), wireless (such as for example Wi-Fi or WorldwideInteroperability for Microwave Access (WiMAX)), or optical (such as forexample Synchronous Optical Network (SONET) or Synchronous DigitalHierarchy (SDH)) links. In particular embodiments, one or more links 150each include an ad hoc network, an intranet, an extranet, a VPN, a LAN,a WLAN, a WAN, a WWAN, a MAN, a portion of the Internet, a portion ofthe PSTN, a cellular technology-based network, a satellitecommunications technology-based network, another link 150, or acombination of two or more such links 150. Links 150 need notnecessarily be the same throughout network environment 100. One or morefirst links 150 may differ in one or more respects from one or moresecond links 150.

In particular embodiments, client system 130 may be an electronic deviceincluding hardware, software, or embedded logic components or acombination of two or more such components and capable of carrying outthe appropriate functionalities implemented or supported by clientsystem 130. As an example and not by way of limitation, a client system130 may include a computer system such as a desktop computer, notebookor laptop computer, netbook, a tablet computer, e-book reader, GPSdevice, camera, personal digital assistant (PDA), handheld electronicdevice, cellular telephone, smartphone, other suitable electronicdevice, or any suitable combination thereof. This disclosurecontemplates any suitable client systems 130. A client system 130 mayenable a network user at client system 130 to access network 110. Aclient system 130 may enable its user to communicate with other users atother client systems 130. Client system 130 may access social-networkingsystem 160 directly, via network 110, or via a third-party system. As anexample and not by way of limitation, client system 130 may access athird-party system via social-networking system 160.

In particular embodiments, client system 130 may include various typesof sensors, for example and without limitation: touch sensors (disposed,for example, on a display of the client system, the back of the clientsystem and one or more lateral edges of the client system) for detectinga user touching the surface of the client system (e.g., using one ormore fingers); an accelerometer for detecting whether the client systemis moving and the speed of the movement; a thermometer for measuring thetemperature change near the client system; proximity sensors fordetecting the proximity of the client system to another object (e.g., ahand, desk, or other object); light sensors for measuring the ambientlight around the client system; imaging sensors (e.g., camera) forcapturing digital still images and/or video of objects near the clientsystem (e.g., scenes, people, bar codes, QR codes, etc.); locationsensors (e.g., Global Positioning System (GPS)) for determining thelocation (e.g., in terms of latitude and longitude) of the clientsystem; sensors for detecting communication networks within closeproximity (e.g., near field communication (NFC), Bluetooth, RFID,infrared); chemical sensors; and biometric sensors for biometrics-based(e.g., fingerprint, palm vein pattern, hand geometry, iris/retina, DNA,face, voice, olfactory, sweat) authentication of a user of clientsystem. This disclosure contemplates that a client system may includeany applicable type of sensor. Sensors may provide various types ofsensor data, which may be analyzed to determine the user's intentionwith respect to the client system at a given time.

Client system 130 may include an automatic screen timeout setting thatis associated with a countdown to the initiation of the screen timeout.An automatic screen timeout may control how long it takes the screen topower down when client system 130 is not being used. An automatic screentimeout may secure client system 130, preventing unauthorized access ordata loss if client system is lost or stolen. Where client system 130 isbattery operated, an automatic screen timeout may improve powermanagement by increasing battery life as a result of reducing batteryusage by the screen. In particular embodiments, the countdown specifieshow much idle time (e.g. continuous time without user interaction withclient system 130) must elapse before the screen turns off. Thecountdown may be a time of 1 second up to the screen being always on. Inparticular embodiments, the countdown may be fixed where the countdownis determined by a preset time that is preprogrammed into client system130 or a default time determined by social-networking system 160. Inparticular embodiments, the countdown may be adaptive where thecountdown is initially determined by either a preset time of clientsystem 130 or determined by social-networking system 160, but thenchanges in response to various user scenarios.

FIG. 2 illustrates an example timeline of an example automatic screentimeout according to one embodiment. In call 202, user 101 isinteracting with a screen of client system 130. Interacting with ascreen may include, but is not limited to, touching the screen of clientsystem 130, running one or more applications on client system 130,accessing, sending data to, and receiving data from social-networkingsystem 160, and holding client system 130 near user 101 or at aparticular angle. For each occurrence where user 101 is no longerinteracting with the screen of client system 130, a countdown toinitiation of an automatic screen timeout begins counting down. Atcompletion of the countdown, client system 130 initiates the automaticscreen timeout and turns off the screen.

In call 204, user 101 wakes up the screen of client system 130 within afirst pre-determined amount of time. For example, if the countdown wastoo short, user 101 may wake up the screen of client system 130 withinthe first pre-determined amount of time after the automatic screentimeout turned off the screen. Client system 130 may determine aduration underage of the countdown for each occurrence of the automaticscreen timeout that was too short. Client system 130 adjusts a length ofthe countdown based at least in part on the duration underages.

In call 206, user 101 interacts with the screen of client system 130 ina same or similar manner as described above with respect to call 202.For each occurrence where user 101 is no longer interacting with thescreen of client 130, a countdown to initiation of an automatic screentimeout begins counting down. In call 208, user turns off the screen ofclient system 130 within a second pre-determined amount of time. Forexample, if the countdown was too long, user 101 may turn off the screenof client system 130 within the second pre-determined amount of timeprior to initiation of the automatic screen timeout. Client system 130may determine a duration overage of the countdown for each occurrence ofthe automatic screen timeout with a countdown that was too long. Clientsystem 130 adjusts the length of the countdown based at least in part onthe duration overages in addition to the duration underages. Particularembodiments may repeat one or more calls and steps described here withrespect to FIG. 2, where appropriate. Although this disclosure describesand illustrates particular calls occurring in a particular order, thisdisclosure contemplates any suitable calls of FIG. 2 occurring in anysuitable order.

Users of client system 130 may have an experience where the duration ofthe countdown for an automatic screen timeout is too short. That is, auser may be interacting with client device 130, a user may pause frominteracting with client device for some amount of time, the screen goesblack and is black for a time, and the user must then tap on the screenand re-login to client system 130. FIG. 3 illustrates an example methodfor adjusting a length of a countdown based at least in part on durationunderages of the countdown. The method may begin at step 310, where acomputing device determines whether a duration of a countdown to aninitiation of a screen timeout is too short. The countdown to aninitiation of a screen timeout may be too short where the user interactswith client device 130 in order to wake it up within a firstpre-determined amount of time after initiation of the automatic screentimeout. A first pre-determined amount of time after initiation of theautomatic screen timeout may be any time between 0.01 seconds andinfinity.

At step 320, the computing device determines a duration underage of thecountdown for each occurrence of the automatic screen timeout with acountdown that was too short. In particular embodiments, the durationunderage of the countdown that was too short equals an amount of timefrom initiation of the automatic screen timeout to user interaction withthe computing device waking up the computing device within the firstpre-determined amount of time. At step 330, the computing device adjuststhe length of the countdown based in part on the duration underages. Inparticular embodiments, the countdown may be adjusted to be longer basedon the duration underages.

Users of client system 130 may have an experience where the duration ofthe countdown for an automatic screen timeout is too long. That is, auser may be interacting with client device 130, pause from interactingwith client device 130 for some amount of time, and, before the screentimes out (e.g. goes dark), manually initiate screen timeout. FIG. 4illustrates an example method for adjusting a length of a countdownbased at least in part on duration overages of the countdown in additionto the duration underages. The method may begin at step 410, where acomputing device determines whether a duration of a countdown to aninitiation of a screen timeout is too long. The countdown to theinitiation of an automatic screen timeout may have been too long ifthere was user interaction with the computing device to manuallyinitiate the automatic screen timeout prior to a second pre-determinedamount of time before initiation of the automatic screen timeout. Asecond pre-determined amount of time before initiation of the automaticscreen timeout may be any time between 0.01 seconds and the countdown.

At step 420 the computing device determines a duration overage of thecountdown for each occurrence of the automatic screen timeout with acountdown that was too long. In particular embodiments, the durationoverage of the countdown that was too long equals an amount of time fromthe user manually initiating the automatic screen timeout prior to thesecond pre-determined amount of time before initiation of the automaticscreen timeout. In particular embodiments, the first pre-determinedamount of time and the second pre-determined amount of time are the sameamount of time. In particular embodiments, the first pre-determinedamount of time is shorter than the second pre-determined amount of time.At step 430, the computing device adjusts the length of the countdownbased in part on the duration overages in addition to the durationunderages. In particular embodiments, the countdown may be adjusted tobe longer based on the duration underages and shorter based on theduration overages.

Particular embodiments may repeat one or more steps of the method ofFIGS. 3-4, where appropriate. Although this disclosure describes andillustrates particular steps of the methods of FIGS. 3-4 as occurring ina particular order, this disclosure contemplates any suitable steps ofthe methods of FIGS. 3-4 occurring in any suitable order. Moreover,although this disclosure describes and illustrates particularcomponents, devices, or systems carrying out particular steps of themethods of FIGS. 3-4, this disclosure contemplates any suitablecombination of any suitable components, devices, or systems carrying outany suitable steps of the methods of FIGS. 3-4.

In particular embodiments, the countdown of the automatic screen timeoutwith a countdown to its initiation may be based on data including datafrom social-networking system 160. In particular embodiments, durationunderages or duration overages may be based on social context. Thelength of the countdown may be adjusted based on duration underages andduration overages that are associated with a social context insocial-networking system 160. A social context in social-networkingsystem 160 may include, but are not limited to, any features associatedwith one or more social graphs, actions a user has taken with respect toitems or objects, and profile information of the user. In particularembodiments, for example, the duration underages and duration overagesmay be associated with events logged in social-networking system, suchas a user is at a party at a restaurant with several friends that theuser is associated with on social-networking system 160. In particularembodiments, the duration underages and duration overages may beassociated with situational data of a user, such as time and place.

In particular embodiments, duration underages and duration overages maybe associated with various aspects of client system 130. The length ofthe countdown may be adjusted based on duration underages and durationoverages that are associated with particular applications running onclient system 130, the size of the screen of client system 130, theposition or angle of client system 130, and various inputs from one ormore sensors of client system 130. For example, if a particularapplication is running on client system 130, that may indicate that auser is interacting with client system 130 and that the countdown shouldbe longer. Where a user is running an application, such as a game, thescreen timeout may be disabled. Where a user has recently received amessage, the length of the countdown may be longer because the user mayread the message within an amount of time. As another example, thelength of the countdown may be longer for larger screens of clientsystem 130 where a user may be more likely to read an entire page, asopposed to smaller screens where a user may be less likely to read anentire page and thus the countdown may be shorter. Where an angle ofclient system 130 is between 1 and 90 degrees, the length of thecountdown may be longer because when client system 130 is at such anangle, a user may be more likely to be interacting with client system130. Whereas, if the angle of client system 130 is 0 degrees, this mayindicate that the user is not interacting with client system 130. Inparticular embodiments, sensors, such as light sensors and infraredsensors, may detect distance or location that suggests that a user ismore or less likely to be interacting with client system 130. Forexample, duration underages and duration overages may be associated withan infrared sensor detecting that client system is close to a user'sface. For example, duration underages and duration overages may beassociated with a light sensor detecting little or no light, which mayindicate that a user is not interacting with client system 130 becauseclient system 130 is in a user's pocket.

FIG. 5 illustrates an example computer system 500. In particularembodiments, one or more computer systems 500 perform one or more stepsof one or more methods described or illustrated herein. In particularembodiments, one or more computer systems 500 provide functionalitydescribed or illustrated herein. In particular embodiments, softwarerunning on one or more computer systems 500 performs one or more stepsof one or more methods described or illustrated herein or providesfunctionality described or illustrated herein. Particular embodimentsinclude one or more portions of one or more computer systems 500.Herein, reference to a computer system may encompass a computing device,where appropriate. Moreover, reference to a computer system mayencompass one or more computer systems, where appropriate.

This disclosure contemplates any suitable number of computer systems500. This disclosure contemplates computer system 500 taking anysuitable physical form. As example and not by way of limitation,computer system 500 may be an embedded computer system, a system-on-chip(SOC), a single-board computer system (SBC) (such as, for example, acomputer-on-module (COM) or system-on-module (SOM)), a desktop computersystem, a laptop or notebook computer system, an interactive kiosk, amainframe, a mesh of computer systems, a mobile telephone, a personaldigital assistant (PDA), a server, a tablet computer system, or acombination of two or more of these. Where appropriate, computer system500 may include one or more computer systems 500; be unitary ordistributed; span multiple locations; span multiple machines; spanmultiple data centers; or reside in a cloud, which may include one ormore cloud components in one or more networks. Where appropriate, one ormore computer systems 500 may perform without substantial spatial ortemporal limitation one or more steps of one or more methods describedor illustrated herein. As an example and not by way of limitation, oneor more computer systems 500 may perform in real time or in batch modeone or more steps of one or more methods described or illustratedherein. One or more computer systems 500 may perform at different timesor at different locations one or more steps of one or more methodsdescribed or illustrated herein, where appropriate.

In particular embodiments, computer system 500 includes a processor 502,memory 504, storage 506, an input/output (I/O) interface 508, acommunication interface 510, and a bus 512. Although this disclosuredescribes and illustrates a particular computer system having aparticular number of particular components in a particular arrangement,this disclosure contemplates any suitable computer system having anysuitable number of any suitable components in any suitable arrangement.

In particular embodiments, processor 502 includes hardware for executinginstructions, such as those making up a computer program. As an exampleand not by way of limitation, to execute instructions, processor 502 mayretrieve (or fetch) the instructions from an internal register, aninternal cache, memory 504, or storage 506; decode and execute them; andthen write one or more results to an internal register, an internalcache, memory 504, or storage 506. In particular embodiments, processor502 may include one or more internal caches for data, instructions, oraddresses. This disclosure contemplates processor 502 including anysuitable number of any suitable internal caches, where appropriate. Asan example and not by way of limitation, processor 502 may include oneor more instruction caches, one or more data caches, and one or moretranslation lookaside buffers (TLBs). Instructions in the instructioncaches may be copies of instructions in memory 504 or storage 506, andthe instruction caches may speed up retrieval of those instructions byprocessor 502. Data in the data caches may be copies of data in memory504 or storage 506 for instructions executing at processor 502 tooperate on; the results of previous instructions executed at processor502 for access by subsequent instructions executing at processor 502 orfor writing to memory 504 or storage 506; or other suitable data. Thedata caches may speed up read or write operations by processor 502. TheTLBs may speed up virtual-address translation for processor 502. Inparticular embodiments, processor 502 may include one or more internalregisters for data, instructions, or addresses. This disclosurecontemplates processor 502 including any suitable number of any suitableinternal registers, where appropriate. Where appropriate, processor 502may include one or more arithmetic logic units (ALUs); be a multi-coreprocessor; or include one or more processors 502. Although thisdisclosure describes and illustrates a particular processor, thisdisclosure contemplates any suitable processor.

In particular embodiments, memory 504 includes main memory for storinginstructions for processor 502 to execute or data for processor 502 tooperate on. As an example and not by way of limitation, computer system500 may load instructions from storage 506 or another source (such as,for example, another computer system 500) to memory 504. Processor 502may then load the instructions from memory 504 to an internal registeror internal cache. To execute the instructions, processor 502 mayretrieve the instructions from the internal register or internal cacheand decode them. During or after execution of the instructions,processor 502 may write one or more results (which may be intermediateor final results) to the internal register or internal cache. Processor502 may then write one or more of those results to memory 504. Inparticular embodiments, processor 502 executes only instructions in oneor more internal registers or internal caches or in memory 504 (asopposed to storage 506 or elsewhere) and operates only on data in one ormore internal registers or internal caches or in memory 504 (as opposedto storage 506 or elsewhere). One or more memory buses (which may eachinclude an address bus and a data bus) may couple processor 502 tomemory 504. Bus 512 may include one or more memory buses, as describedbelow. In particular embodiments, one or more memory management units(MMUs) reside between processor 502 and memory 504 and facilitateaccesses to memory 504 requested by processor 502. In particularembodiments, memory 504 includes random access memory (RAM). This RAMmay be volatile memory, where appropriate Where appropriate, this RAMmay be dynamic RAM (DRAM) or static RAM (SRAM).

Moreover, where appropriate, this RAM may be single-ported ormulti-ported RAM. This disclosure contemplates any suitable RAM. Memory504 may include one or more memories 504, where appropriate. Althoughthis disclosure describes and illustrates particular memory, thisdisclosure contemplates any suitable memory.

In particular embodiments, storage 506 includes mass storage for data orinstructions. As an example and not by way of limitation, storage 506may include a hard disk drive (HDD), a floppy disk drive, flash memory,an optical disc, a magneto-optical disc, magnetic tape, or a UniversalSerial Bus (USB) drive or a combination of two or more of these. Storage506 may include removable or non-removable (or fixed) media, whereappropriate. Storage 506 may be internal or external to computer system500, where appropriate. In particular embodiments, storage 506 isnon-volatile, solid-state memory. In particular embodiments, storage 506includes read-only memory (ROM). Where appropriate, this ROM may bemask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM),electrically erasable PROM (EEPROM), electrically alterable ROM (EAROM),or flash memory or a combination of two or more of these. Thisdisclosure contemplates mass storage 506 taking any suitable physicalform. Storage 506 may include one or more storage control unitsfacilitating communication between processor 502 and storage 506, whereappropriate. Where appropriate, storage 506 may include one or morestorages 506. Although this disclosure describes and illustratesparticular storage, this disclosure contemplates any suitable storage.

In particular embodiments, I/O interface 508 includes hardware,software, or both providing one or more interfaces for communicationbetween computer system 500 and one or more I/O devices. Computer system500 may include one or more of these I/O devices, where appropriate. Oneor more of these I/O devices may enable communication between a personand computer system 500. As an example and not by way of limitation, anI/O device may include a keyboard, keypad, microphone, monitor, mouse,printer, scanner, speaker, still camera, stylus, tablet, touch screen,trackball, video camera, another suitable I/O device or a combination oftwo or more of these. An I/O device may include one or more sensors.This disclosure contemplates any suitable I/O devices and any suitableI/O interfaces 508 for them. Where appropriate, I/O interface 508 mayinclude one or more device or software drivers enabling processor 502 todrive one or more of these I/O devices. I/O interface 508 may includeone or more I/O interfaces 508, where appropriate. Although thisdisclosure describes and illustrates a particular I/O interface, thisdisclosure contemplates any suitable I/O interface.

In particular embodiments, communication interface 510 includeshardware, software, or both providing one or more interfaces forcommunication (such as, for example, packet-based communication) betweencomputer system 500 and one or more other computer systems 500 or one ormore networks. As an example and not by way of limitation, communicationinterface 510 may include a network interface controller (NIC) ornetwork adapter for communicating with an Ethernet or other wire-basednetwork or a wireless NIC (WNIC) or wireless adapter for communicatingwith a wireless network, such as a WI-FI network. This disclosurecontemplates any suitable network and any suitable communicationinterface 510 for it. As an example and not by way of limitation,computer system 500 may communicate with an ad hoc network, a personalarea network (PAN), a local area network (LAN), a wide area network(WAN), a metropolitan area network (MAN), or one or more portions of theInternet or a combination of two or more of these. One or more portionsof one or more of these networks may be wired or wireless. As anexample, computer system 500 may communicate with a wireless PAN (WPAN)(such as, for example, a BLUETOOTH WPAN), a WI-FI network, a WI-MAXnetwork, a cellular telephone network (such as, for example, a GlobalSystem for Mobile Communications (GSM) network), or other suitablewireless network or a combination of two or more of these. Computersystem 500 may include any suitable communication interface 510 for anyof these networks, where appropriate. Communication interface 510 mayinclude one or more communication interfaces 510, where appropriate.Although this disclosure describes and illustrates a particularcommunication interface, this disclosure contemplates any suitablecommunication interface.

In particular embodiments, bus 512 includes hardware, software, or bothcoupling components of computer system 500 to each other. As an exampleand not by way of limitation, bus 512 may include an AcceleratedGraphics Port (AGP) or other graphics bus, an Enhanced Industry StandardArchitecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT)interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBANDinterconnect, a low-pin-count (LPC) bus, a memory bus, a Micro ChannelArchitecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, aPCI-Express (PCIe) bus, a serial advanced technology attachment (SATA)bus, a Video Electronics Standards Association local (VLB) bus, oranother suitable bus or a combination of two or more of these. Bus 512may include one or more buses 512, where appropriate. Although thisdisclosure describes and illustrates a particular bus, this disclosurecontemplates any suitable bus or interconnect.

Herein, a computer-readable non-transitory storage medium or media mayinclude one or more semiconductor-based or other integrated circuits(ICs) (such, as for example, field-programmable gate arrays (FPGAs) orapplication-specific ICs (ASICs)), hard disk drives (HDDs), hybrid harddrives (HHDs), optical discs, optical disc drives (ODDs),magneto-optical discs, magneto-optical drives, floppy diskettes, floppydisk drives (FDDs), magnetic tapes, solid-state drives (SSDs),RAM-drives, SECURE DIGITAL cards or drives, any other suitablecomputer-readable non-transitory storage media, or any suitablecombination of two or more of these, where appropriate. Acomputer-readable non-transitory storage medium may be volatile,non-volatile, or a combination of volatile and non-volatile, whereappropriate.

Herein, “or” is inclusive and not exclusive, unless expressly indicatedotherwise or indicated otherwise by context. Therefore, herein, “A or B”means “A, B, or both,” unless expressly indicated otherwise or indicatedotherwise by context. Moreover, “and” is both joint and several, unlessexpressly indicated otherwise or indicated otherwise by context.Therefore, herein, “A and B” means “A and B, jointly or severally,”unless expressly indicated otherwise or indicated otherwise by context.

The scope of this disclosure encompasses all changes, substitutions,variations, alterations, and modifications to the example embodimentsdescribed or illustrated herein that a person having ordinary skill inthe art would comprehend. The scope of this disclosure is not limited tothe example embodiments described or illustrated herein. Moreover,although this disclosure describes and illustrates respectiveembodiments herein as including particular components, elements,functions, operations, or steps, any of these embodiments may includeany combination or permutation of any of the components, elements,functions, operations, or steps described or illustrated anywhere hereinthat a person having ordinary skill in the art would comprehend.Furthermore, reference in the appended claims to an apparatus or systemor a component of an apparatus or system being adapted to, arranged to,capable of, configured to, enabled to, operable to, or operative toperform a particular function encompasses that apparatus, system,component, whether or not it or that particular function is activated,turned on, or unlocked, as long as that apparatus, system, or componentis so adapted, arranged, capable, configured, enabled, operable, oroperative.

What is claimed is:
 1. A method comprising: by a computing device, determining for each of a plurality of countdowns to an automatic screen timeout of the computing device whether the countdown was too long or too short, the countdown being too short if user interaction with the computing device occurred within a first pre-determined amount of time after the automatic screen timeout, the countdown being too long if user interaction with the computing device turned off a screen of the computing device prior to a second pre-determined amount of time before the automatic screen timeout; by the computing device, determining an underage of each of one or more of the countdowns that was too short; by the computing device, determining an overage of each of one or more of the countdowns that was too long; and by the computing device, adjusting a countdown length of the automatic screen timeout based at least in part on the underages or overages.
 2. The method of claim 1, wherein the first pre-determined amount of time equals the second pre-determined amount of time.
 3. The method of claim 1, wherein the first pre-determined amount of time is shorter than the second pre-determined amount of time.
 4. The method of claim 1, wherein an overage of a countdown that was too long equals the second pre-determined amount of time.
 5. The method of claim 1, wherein an underage of a countdown that was too short equals an amount of time from the automatic screen timeout to user interaction with the computing device within the first pre-determined amount of time.
 6. The method of claim 1, wherein the computing device is a smartphone.
 7. One or more computer-readable non-transitory storage media embodying software that is configured when executed to: determine for each of a plurality of countdowns to an automatic screen timeout of a computing device whether the countdown was too long or too short, the countdown being too short if user interaction with the computing device occurred within a first pre-determined amount of time after the automatic screen timeout, the countdown being too long if user interaction with the computing device turned off a screen of the computing device prior to a second pre-determined amount of time before the automatic screen timeout; determine an underage of each of one or more of the countdowns that was too short; determine an overage of each of one or more of the countdowns that was too long; and adjust a countdown length of the automatic screen timeout based at least in part on the underages or overages.
 8. The media of claim 7, wherein the first pre-determined amount of time equals the second pre-determined amount of time.
 9. The media of claim 7, wherein the first pre-determined amount of time is shorter than the second pre-determined amount of time.
 10. The media of claim 7, wherein an overage of a countdown that was too long equals the second pre-determined amount of time.
 11. The media of claim 7, wherein an underage of a countdown that was too short equals an amount of time from the automatic screen timeout to user interaction with the computing device within the first pre-determined amount of time.
 12. The media of claim 7, wherein the computing device is a smartphone.
 13. A computing device comprising: one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors being operable when executing the instructions to: determine for each of a plurality of countdowns to an automatic screen timeout of the computing device whether the countdown was too long or too short, the countdown being too short if user interaction with the computing device occurred within a first pre-determined amount of time after the automatic screen timeout, the countdown being too long if user interaction with the computing device turned off a screen of the computing device prior to a second pre-determined amount of time before the automatic screen timeout; determine an underage of each of one or more of the countdowns that was too short; determine an overage of each of one or more of the countdowns that was too long; and adjust a countdown length of the automatic screen timeout based at least in part on the underages or overages.
 14. The computing device of claim 13, wherein the first pre-determined amount of time equals the second pre-determined amount of time.
 15. The computing device of claim 13, wherein the first pre-determined amount of time is shorter than the second pre-determined amount of time.
 16. The computing device of claim 13, wherein an overage of a countdown that was too long equals the second pre-determined amount of time.
 17. The computing device of claim 13, wherein an underage of a countdown that was too short equals an amount of time from the automatic screen timeout to user interaction with the computing device within the first pre-determined amount of time.
 18. The computing device of claim 13, wherein the computing device is a smartphone. 